Skip to content

chore: merge main to next#1798

Open
igamigo wants to merge 9 commits intonextfrom
igamigo-merge-main
Open

chore: merge main to next#1798
igamigo wants to merge 9 commits intonextfrom
igamigo-merge-main

Conversation

@igamigo
Copy link
Collaborator

@igamigo igamigo commented Mar 16, 2026

To be merged without squash

@igamigo igamigo changed the base branch from next to main March 16, 2026 19:05
@igamigo igamigo changed the base branch from main to next March 16, 2026 19:06
@igamigo igamigo marked this pull request as ready for review March 16, 2026 19:14
Copy link
Contributor

@bobbinth bobbinth left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good! Thank you!

- Fixed `bundled bootstrap` requiring `--validator.key.hex` or `--validator.key.kms-id` despite a default key being configured ([#1732](https://github.com/0xMiden/node/pull/1732)).
- Fixed incorrectly classifying private notes with the network attachment as network notes ([#1378](https://github.com/0xMiden/node/pull/1738)).
- Fixed accept header version negotiation rejecting all pre-release versions; pre-release label matching is now lenient, accepting any numeric suffix within the same label (e.g. `alpha.3` accepts `alpha.1`) ([#1755](https://github.com/0xMiden/node/pull/1755)).
## v0.13.8 (2026-03-12)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
## v0.13.8 (2026-03-12)
## v0.13.8 (2026-03-12)

@Mirko-von-Leipzig
Copy link
Collaborator

To be merged without squash

If we are following the separate branches approach, then we could squash merge this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants